# Sample

What are the gotchas when upgrading eks from 1.18 to the latest version?

Compatibility issues with add-ons and custom resources: 
  Some add-ons and custom resources may not be compatible 
  with the latest version of EKS and may need to be updated or replaced.

Changes in Kubernetes API: 
  Upgrading to a new version of EKS may also result in changes 
  to the Kubernetes API, which could affect existing applications and services.

Cluster scaling limitations: 
  The latest version of EKS may have different limitations on the 
  number of nodes and pods that can be added to a cluster, 
  which may require adjustments to the cluster scaling strategy.

Node pool compatibility: 
  If you are using node pools, you may need to update them to 
  ensure compatibility with the latest version of EKS.

Cluster upgrades may cause downtime:
  Upgrading to a new version of EKS can be a complex process, and 
  it may cause some downtime for your applications and services.

Additional testing and validation: 
  Upgrading to a new version of EKS may require additional testing and 
  validation to ensure that your applications and services are working correctly.

Networking and security configurations: 
  Upgrading to a new version of EKS may require changes to the networking and 
  security configurations of the cluster, 
  which could affect existing applications and services.

Monitoring and logging:
  Upgrading to a new version of EKS may require changes to the monitoring and 
  logging configurations of the cluster, 
  which could affect existing applications and services.